Item delivery with an aerial vehicle

ABSTRACT

Described is a system and method for utilizing unmanned aerial vehicles (“UAV”) to facilitate delivery of ordered items to user specified delivery destinations. In one implementation, the UAV may be configured as a one-way UAV that is designed to transport ordered items to the user specified delivery destination but not return to a materials handling facility under its own power. Instead, the one-way UAV may remain at the delivery destination for later retrieval by a retrieval unit (e.g., truck).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.14/623,465, filed Feb. 16, 2015, the contents of which are incorporatedby reference herein in their entirety.

BACKGROUND

Many companies package items and/or groups of items together for avariety of purposes, such as e-commerce and mail-order companies thatpackage items (e.g., books, CDs, apparel, food, etc.) to be shipped tofulfill orders from customers. Retailers, wholesalers, and other productdistributors (which may collectively be referred to as distributors)typically maintain an inventory of various items that may be ordered bycustomers. This inventory may be maintained and processed at a buildingincluding a materials handling facility. Such materials handlingfacilities may include, but are not limited to, one or more of:warehouses, distribution centers, cross-docking facilities, orderfulfillment facilities, packaging facilities, shipping facilities, orother facilities or combinations of facilities for performing one ormore functions of material (inventory) handling.

Typically ordered items are packed in shipping packages (e.g.,corrugated boxes) and shipped to the customer's residence or place ofbusiness. Physical delivery of items to user specified deliverydestinations has improved dramatically over the years, with someretailers offering next day delivery of ordered items. The final, orlast mile delivery of physical items to a user specified deliverydestination, is traditionally accomplished using a human controlledtruck, bicycle, cart, etc. For example, a user may order an item fordelivery to their home. The item may be picked from a materials handlingfacility, packed, and shipped to the customer for final delivery by ashipping carrier. The shipping carrier will load the item onto a truckthat is driven by a human to the final delivery destination and thehuman driver, or another human companion with the driver, will retrievethe item from the truck and complete the delivery to the destination.For example, the human may hand the item to a recipient, place the itemon the user's porch, store the item in a post office box, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 is a block diagram of a delivery environment that utilizesone-way unmanned aerial vehicles for item delivery, according to animplementation.

FIG. 2 is an illustration of a one-way unmanned aerial vehicle,according to an implementation.

FIG. 3 is a flow diagram of an example item delivery process, accordingto an implementation.

FIG. 4 is a flow diagram of an example one-way unmanned aerial vehicleretrieval process, according to an implementation.

FIG. 5 is a block diagram of an example one-way unmanned aerial vehiclecontrol system, according to an implementation.

FIG. 6 is a block diagram of an illustrative implementation of a serversystem that may be used with various implementations.

While implementations are described herein by way of example, thoseskilled in the art will recognize that the implementations are notlimited to the examples or drawings described. It should be understoodthat the drawings and detailed description thereto are not intended tolimit implementations to the particular form disclosed but, on thecontrary, the intention is to cover all modifications, equivalents andalternatives falling within the spirit and scope as defined by theappended claims. As used throughout this application, the word “may” isused in a permissive sense (i.e., meaning having the potential to),rather than the mandatory sense (i.e., meaning must). Similarly, thewords “include,” “including,” and “includes” mean including, but notlimited to.

DETAILED DESCRIPTION

This disclosure describes systems and methods for utilizing unmannedaerial vehicles (“UAV”) to facilitate delivery of ordered items to userspecified delivery destinations. In one implementation, the UAV may beconfigured as a one-way UAV that is designed to transport ordered itemsto the user specified delivery destination but not return to a materialshandling facility under its own power. Instead, the one-way UAV mayremain at the delivery destination for later retrieval by a retrievalunit (e.g., truck). In other implementations, the one-way UAV may not bereturned. For example, the one-way UAV may be disposable, part of theitem delivered to the user, and/or made of recyclable material.

In some implementations, the one-way UAV may be configured as a small,low cost UAV that is designed to transport only small, lightweightitems. For example, the one-way UAV may be configured to only be capableof carrying a payload having a weight of approximately one pound or less(referred to herein as carrying weight). By reducing the carrying weightof the one-way UAV, the total weight of the one-way UAV may likewise besmaller. For example, the frame of the one-way UAV, motors, propellers,etc., may be smaller. By reducing the carrying weight and total weightof the one-way UAV, the power supply necessary to power the one-way UAV,etc., may likewise be smaller, further reducing the total weight of theone-way UAV. Likewise, in some implementations, the one-way UAV may beutilized in a system in which the one-way UAV only has power sufficientto enable aerial navigation from the materials handling facility to theuser specified delivery destination, thereby further reducing the powerrequirements and overall weight of the one-way UAV.

By reducing the size and weight of the one-way UAV and the carryingcapacity of the one-way UAV, the cost to manufacture the one-way UAV andthe potential damage to objects if impacted by the one-way UAV islikewise reduced. For example, if the one-way UAV is landing at adelivery destination and impacts an object, the smaller form factor ofthe one-way UAV, and thus the smaller propeller blades, will causelittle to no damage to the impacted object.

After a one-way UAV completes a delivery to a user specified deliverydestination, the one-way UAV may become inoperable and/or emit a beaconindicating that it is to be retrieved by a retrieval unit. A retrievalunit, such as a ground based vehicle (e.g., car, truck, bus), maynavigate a retrieval route and retrieve one or more one-way UAVs and/orother items along the retrieval route. Once the one-way UAVs areretrieved by the retrieval unit, the retrieval unit may return theone-way UAVs to the materials handling facility, or another location,and the one-way UAVs may be utilized to transport another ordered itemto another delivery destination.

FIG. 1 is a block diagram of a delivery environment 100 that includes aone-way UAV 112 and a retrieval unit 108, according to animplementation. The delivery environment 100 includes a user interfacethat allows a user 104 to place an order for an item that is to bedelivered to the user. The user interface may be a graphical userinterface, an audio only interface, a multi-mode interface, or any otherinterface for interacting with the user 104. The user interface may beprovided to the user 104 through any type of electronic device 106, suchas a tablet, desktop, laptop, smart phone, personal digital assistant,netbook, etc. The user interface may be delivered to the electronicdevice 106 by one or more remote computing resources 110 that make uppart or all of an electronic-commerce (e-commerce) shopping environment.In other implementations, the user interface may provide a directcommunication between a user and an agent.

The remote computing resources 110 may form a portion of anetwork-accessible computing platform implemented as a computinginfrastructure of processors, storage, software, data access, and othercomponents that is maintained and accessible via a network. Services,such as e-commerce shopping services, offered by the remote computingresources 110 do not require that the user have knowledge of thephysical location and configuration of the system that delivers theservices. The electronic device 106 may communicatively couple to theremote computing resources 110 via the network which may represent wiredtechnologies (e.g., wires, USB, fiber optic cable, etc.), wirelesstechnologies (e.g., RF, cellular, satellite, Bluetooth, etc.), and/orother connection technologies. The network carries data between theelectronic device 106 and the remote computing resources 110.

After receiving from a user 104 an order for an item, the electronicdevice 106 may send this information to the remote computing resources110 over the network. As illustrated, the remote computing resources 110may include one or more servers, such as servers 120(1), 120(2) . . .120(N). These servers 120(1)-(N) may be arranged in any number of ways,such as server farms, stacks, and the like that are commonly used indata centers. Furthermore, the servers 120(1)-(N) may include one ormore processors 122 and memory 124 that may store an inventorymanagement system 126 and/or a retrieval route management system 128.

The inventory management system 126 may be configured, for example, toperform order planning and fulfillment of the order from materialshandling facility 130 using a one-way UAV 112 and/or by traditionaldelivery mechanism (e.g., vehicles). The memory 124 of the remotecomputing resources 110 may also include a retrieval route managementsystem 128 configured to plan retrieval routes for retrieval of one-wayUAVs 112. The inventory management system 126 may communicate with theretrieval route management system 128 providing, for example, locationinformation of delivery destinations and delivery times identifying thelocation and time when one-way UAVs will complete a delivery of an itemat a user specified delivery destination. In some implementations, theone-way UAV 112 may also communicate with the retrieval route managementsystem 128 to inform the retrieval route management system 128 that theone-way UAV is to be retrieved. For example, the one-way UAV 112 mayemit a beacon upon delivery completion that includes a one-way UAVidentifier and a location of the one-way UAV (e.g., global positioningcoordinates).

In some implementations, rather than the UAV being retrieved by aretrieval unit from the delivery destination, the user 104 may place theone-way UAV in a UAV retrieval container 114. For example, UAV retrievalcontainers 114 may be positioned at convenient locations (e.g., parkinglots, office buildings, public places). The retrieval route managementsystem 128 may send a request, such as an electronic mail (e-mail),short message (SMS), and multimedia message (MMS) to the user 104requesting that the user 104 place the one-way UAV 112 in a UAVretrieval container 114. Because of the small form factor of the one-wayUAV 112, as discussed further below with respect to FIG. 2, the user mayeasily carry the one-way UAV 112 with them and place the one-way UAV 112into a UAV retrieval container 114.

In still other implementations, rather than requiring a retrieval unitto navigate to and retrieve the one-way UAV 112, the user 104 may sendthe one-way UAV 112 to a return address using traditional transportationtechniques (e.g., traditional ground based shipping carriers). Forexample, included in the one-way UAV 112 with the ordered item may be apre-addressed, pre-paid, shipping pouch or bag into which the one-wayUAV 112 may be placed for return shipping to the materials handlingfacility 130, or another location.

In still other implementations, the one-way UAV may have sufficientpower to travel from the delivery destination to another location (e.g.,another delivery destination, a designated retrieval location, back tothe materials handling facility). For example, in some implementations,there may be designated retrieval locations and the one-way UAVs may beconfigured to travel under their owner power from the materials handlingfacility to the delivery destination, deliver the item, and then travelunder their own power from the delivery destination to a retrievallocation. The retrieval location may be, for example, another materialshandling facility, a rooftop or other structure on which one-way UAVsmay land, etc. If the retrieval location is not the materials handlingfacility, the retrieval management system 128 may plan a retrieval routethat includes retrieval of the one-way UAVs from the retrieval location.

In still another implementation, the one-way UAVs may not be returned tothe materials handling facility. For example, the one-way UAVs may bedisposable. In some implementations, all or part of the one-way UAV maybe manufactured from materials that are recyclable, biodegradable, etc.In still another example, all or part of the one-way UAV may be part orall of the ordered item. For example, as discussed below, the memoryand/or the power module (e.g., battery) of the one-way UAV may be theordered item.

Returning to FIG. 1, when the UAV 112 has completed delivery of the itemto the delivery destination 113, the retrieval management system 128 mayplan a retrieval route that is navigated by a retrieval unit 108 toretrieve the one-way UAV from a retrieval location. The retrievallocation may be the delivery destination 113, a return container 114, oranother location from which the one-way UAV 112 is to be retrieved. Insome implementations, the retrieval management system may plan aretrieval route for the retrieval unit 108 that includes retrieval ofmultiple one-way UAVs 112 and/or retrieval of other items. For example,inventory to be added to the materials handling facility 130, itemsbeing returned by users, items being shipped by users, and/or any otheritem (generally referred to herein as other items, or another item) thatmay be retrieved by the retrieval unit 108, may be included as part ofthe retrieval route planned for the retrieval unit 108. In someimplementations, the retrieval route may include delivery of otheritems. For example, the retrieval route may include locations to whichitems carried by the retrieval unit are to be delivered.

In some implementations, the user may communicate with the remotecomputing system 110 and identify when they will place the one-way UAV112 at a retrieval location for retrieval by the retrieval unit 108. Forexample, after the user ordered item has been delivered, the retrievalmanagement system may plan one or more retrieval routes that includeretrieval of the one-way UAV and send a message to the user 104providing options as to when the user would like the one-way UAV 112retrieved. For example, the retrieval management system 128 may planmultiple retrieval routes, each including a retrieval of the one-way UAV112 from a retrieval location at different times and request that theuser select a preferred time for the retrieval of the one-way UAV 112.Upon selection of a preferred time, the retrieval location may be addedto the retrieval route for retrieval by the retrieval unit 108. In someimplementations, prior to the retrieval unit 108 arriving at theretrieval location, the retrieval management system 128 may send amessage to the user 104 reminding the user that the retrieval unit 108will be arriving to retrieve the one-way UAV 112.

As the retrieval unit 108 retrieves the one-way UAVs and/or other items,the one-way UAVs 112 may be placed into the retrieval unit andtransported by the retrieval unit back to the materials handlingfacility 130, to another materials handling facility and/or to anotherlocation. In some implementations, in addition to transporting theone-way UAVs, the retrieval unit may also be configured to recharge thepower modules of the one-way UAVs 112 as the retrieval unit 108 istransporting the one-way UAVs 112. For example, the retrieval unit mayinclude multiple charging stations (not shown) and, when a one-way UAV112 is retrieved from a retrieval location, the one-way UAV 112 may beconnected to the charging station and the power module of the one-wayUAV 112 may be recharged as it is transported by the retrieval unit 108.By charging the one-way UAVs 112 as they are being transported from aretrieval location back to the materials handling facility 130, oranother location, the one-way UAVs 112 may be ready for subsequentdeployment by the inventory management system 126 to deliver anotheritem soon after they are returned to the materials handling facility130. In other implementations, when the one-way UAVs are returned to thematerials handling facility 130, or another location, they may berecharged (or recharging completed) and/or repaired before they areutilized to transport another item from the materials handling facility130.

FIG. 2 illustrates a block diagram of a top-down view of a one-way UAV212, according to an implementation. The one-way UAV 212 may be designedto be low cost, have a small form factor and limited components, therebyreducing cost of the one-way UAV, power requirements to aeriallynavigate the one-way UAV and reduced or eliminated potential damage ifthe one-way UAV impacts an object. For example, the one-way UAV 212 maybe designed to include only components necessary to achieve flight andnavigate to a delivery destination. Likewise, if the one-way UAV 212 isconfigured to carry a payload 203 up to approximately one pound, thelength and width of the one-way UAV 212 may be equal to or less thantwelve inches and have a weight of approximately five pounds. In otherimplementations, the dimensions and/or weight may be greater or lessthan those illustrated.

As illustrated, the one-way UAV 212 includes four propellers 202-1,202-2, 202-3, 202-4 spaced about the frame 204 of the one-way UAV 212.The propellers 202 may be any form of propeller (e.g., graphite, carbonfiber, plastic) and of a size sufficient to lift the UAV 212 and anyitem carried by or coupled to the one-way UAV 212 so that the UAV 212can navigate through the air, for example, to deliver an item. In someimplementations, the propellers 202 may be formed of a soft, orsemi-soft material, such as a closed-cell extruded polystyrene foam(e.g., Styrofoam®). In other implementations, the propellers may beformed of biodegradable and/or recyclable materials, such as cardboard,compostable plastic, or the like.

In some implementations, the propellers 202 may be of a size sufficientto lift the one-way UAV 212 and a payload 203 having a weight of up toapproximately one pound (carrying weight). In other implementations, thecarrying weight of the one-way UAV 212 may be greater or less thanapproximately one pound. While this example includes four propellers, inother implementations, more or fewer propellers may be utilized.Likewise, in some implementations, the propellers may be positioned atdifferent locations on the one-way UAV 212. In addition, alternativemethods of propulsion may be utilized. For example, fans, jets,turbojets, turbo fans, jet engines, and the like may be used to propelthe one-way UAV 212.

The frame 204 or body of the UAV 212 may likewise be of any suitablematerial, such as graphite, carbon fiber, plastic, and/or aluminum.Likewise, in some implementations, the frame 204, or parts thereof, maybe formed using biodegradable and/or recyclable materials.

In this example, the frame 204 of the UAV 212 includes a payloadcontainer 214 and four motor arms 205-1, 205-2, 205-3, 205-4, or beamsextending from the payload container. The payload container 214 isconfigured to receive or couple with a payload 203, such as an ordereditem. In this example, the payload container 214 is configured as acavity having four sides and a base into which a payload 203 may beplaced. In other implementations, the payload container may have otherconfigurations to hold, couple, or otherwise carry the payload 203. Insome implementations, the payload container 214 may not be part of theone-way UAV but may be attached or coupled with the one-way UAV totransport the item. For example, motor arms 205-1 and 205-3 may be asingle motor arm and motor arms 205-2 and 205-4 may be single motor arm.In such an implementation, the two motor arms may cross or join near acenter of the frame 204 of the one-way UAV. The payload container 214may be mounted onto or underneath the motor arms to enable transport ofthe payload 203. In some implementations, the payload container may notbe utilized and the payload 203 may be coupled directly to the frame 204of the one-way UAV 212.

In still other implementations, the original or item packaging of theordered item may include all or part of the UAV 212. For example, ratherthan coupling an ordered item to a one-way UAV, the item packaging ofthe item may include all or part of a one-way UAV. In such animplementation, when an item is ordered, the item package of the itemitself may receive navigation instructions to navigate to a deliverydestination. If the item packaging of the item includes all thecomponents of the one-way UAV, aerial transport and delivery of the itemcan be completed without the use of a separate one-way UAV. In otherimplementations, the item packaging of the item may include portions ofa one-way UAV, such as the power module 213 and/or control system 210.Attachment points may exist on the item packaging to which motor arms205 that include motors 206 and propellers 202 may be attached tocomplete a one-way UAV so that the item can be aerially transported tothe delivery destination.

In some implementations, the one-way UAV may be configured foraerodynamics. For example, the payload container 214 may include a lid215 that is coupled to the payload container 214 at a pivot point toenable access to items placed in the payload container 214. The lid 215may have an aerodynamic shape that encloses the cavity of the payloadcontainer 214. Likewise, the lid 215 may include some or all of thecontrol system 210, power module(s) 213, etc. The payload container 214and/or the lid 215 may be made of any suitable material(s) such asgraphite, carbon fiber, plastic, aluminum, etc.

In some implementations, the one-way UAV 212 may include one or morememory receivers (not shown) configured to receive a memory module, suchas a universal serial bus (USB) drive, compact flash memory module,secure digital (SD) card, micro-SD cart, and/or other memory modules. Insome implementations, the memory receiver may be incorporated into thepayload container 214 and/or into the lid 215.

The memory module may include navigation instructions that are utilizedby the one-way UAV 212 for navigation from the materials handlingfacility to a delivery destination. For example, the navigationinstructions may specify delivery destination coordinates, desiredaltitude for aerial navigation, desired speed, etc. When the memorymodule is inserted into the memory receiver of the one-way UAV 212, theone-way UAV 212 may utilize the navigation instructions included on thememory module to navigate to the delivery destination. In someimplementations, as discussed further below with respect to FIG. 5, theone-way UAV 212 may not receive and/or utilize any additionalinstructions for completing the aerial navigation to the deliverydestination.

In some implementations, the memory module may be the ordered item. Forexample, a user may order a memory module for delivery. The inventorymanagement system, as part of fulfillment of the order, may generate andstore navigation instructions on the ordered memory module and theordered memory module may be inserted into the memory receiver of theone-way UAV 212 to provide the navigation instructions to the one-wayUAV. In such an implementation, when navigation to the deliverydestination is complete, the one-way UAV 212 may cause the navigationinstructions to be removed from the memory module before the memorymodule is removed from the memory receiver. For example, the one-way UAV212 may delete the navigation instructions, format the memory module,etc., when it completes delivery of the item to the deliverydestination.

The motor arms 205 are all approximately the same length and each oneextends from a respective corner of the payload container 214. In otherimplementations, motor arms may be of different lengths and/orpositioned at different locations on the one-way UAV 212.

The propellers 202 and corresponding motors 206-1, 206-2, 206-3, and206-4 are positioned at the ends of each motor arm 205. The motors 206may be any form of motor capable of generating enough speed with theattached propeller 202 to lift the one-way UAV 212 and any includedpayload 203 thereby enabling aerial transport of the payload 203.Similar to the lifting propellers 202, in some implementations, thelifting motors may be selected such that they provide enough rotationalspeed to generate a force from the propellers that is sufficient to liftthe one-way UAV 212 and the payload 203 having a weight of up toapproximately one pound.

Surrounding each propeller 202 is a safety barrier 208-1, 208-2, 208-3,and 208-4. In this example, a safety barrier is positioned around eachpropeller 202. In other implementations, a single safety barrier may bepositioned around the entire one-way UAV 212 in such a manner that themotors and propellers 202 are within the perimeter of the safety barrier208. The safety barrier may be plastic, rubber, etc.

In this example, the one-way UAV control system 210 is incorporated intothe lid 215 of the payload container 214 of the one-way UAV 212. Inother implementations, one or more components of the control system 210may be located at other positions on the one-way UAV. The UAV controlsystem 210, as discussed in further detail below with respect to FIG. 5,controls the operation, routing, navigation, etc., of the one-way UAV212.

The one-way UAV 212 also includes one or more power modules 213. In thisexample, the power module 213 is likewise incorporated into the lid 215of the payload container 214 of the one-way UAV 212. In otherimplementations, the power module 213 may be positioned elsewhere on theone-way UAV 212 and/or may be removably mounted to the one-way UAV 212.The power module 213 for the one-way UAV 212 may be in the form ofbattery power, solar power, gas power, super capacitor, fuel cell,alternative power generation source, or a combination thereof. Inimplementations in which the one-way UAV 212 has a small form factor andis configured to carry a payload of up to approximately one pound, thepower module may be a small lithium-ion polymer battery, polymer lithiumion (Li-poly, Li-Pol, LiPo, LIP, PLI, or Lip) battery, a rechargeablealkaline battery, or the like, that will enable aerial transport by theone-way UAV 212 of a payload of approximately one pound a defineddistance at a defined speed and a defined altitude. For example, thepower module may be of a size sufficient to enable aerial transport ofup to forty miles by the one-way UAV 212 of a payload of up toapproximately one pound. In some implementations, the power module 213may be the ordered item. For example, a user may order a rechargeablebattery for delivery to a delivery destination. The ordered item(rechargeable battery) may be coupled to the one-way UAV and used topower the one-way UAV to the delivery destination. The user may thenremove the ordered item from the one-way UAV upon delivery.

The power module(s) 213 are coupled to and provide power for the one-wayUAV control system 210 and the propeller motors 206. In someimplementations, one or more of the power modules may be configured suchthat it can be autonomously removed and/or replaced with another powermodule while the one-way UAV is landed (e.g., such power modules may beprovided or replaced while the one-way UAV is landed in a retrievalunit). In some implementations, when the one-way UAV is within aretrieval unit, the one-way UAV may engage with a charging member torecharge the power module.

While the implementations of the one-way UAV discussed herein utilizepropellers to achieve and maintain flight, in other implementations, theone-way UAV may be configured in other manners. In one implementation,the one-way UAV may include fixed wings and/or a combination of bothpropellers and fixed wings.

In some implementations, multiple different configurations of one-wayUAV may be utilized. For example, different one-way UAV configurationsmay be available to transport different sizes, shapes, and/or weights ofitems, and/or to transport items different distances from the materialshandling facility. For example, one one-way UAV configuration may bedesigned to aerially transport an item having an item weight of no morethan eight ounces a distance of no more than twenty-five miles from thematerials handling facility. A second one-way UAV may be configured totransport an item having an item weight of no more than one pound adistance of no more than twenty-five miles from the materials handlingfacility. A third one-way UAV may be configured to transport an itemhaving an item weight of no more than eight ounces a distance of no morethan forty miles from the materials handling facility. Based on thedifferent item weights and distances to be traveled, the size, weight,and power requirements of the one-way UAV may vary.

FIG. 3 is a flow diagram illustrating an example item delivery process300, according to an implementation. This process, and each processdescribed herein, may be implemented by the architectures describedherein or by other architectures. The process is illustrated as acollection of blocks in a logical flow graph. Some of the blocksrepresent operations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer readablemedia that, when executed by one or more processors, perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes.

The computer readable media may include non-transitory computer readablestorage media, which may include hard drives, floppy diskettes, opticaldisks, CD-ROMs, DVDs, read-only memories (ROMs), random access memories(RAMs), EPROMs, EEPROMs, flash memory, magnetic or optical cards,solid-state memory devices, or other types of storage media suitable forstoring electronic instructions. In addition, in some implementations,the computer readable media may include a transitory computer readablesignal (in compressed or uncompressed form). Examples of computerreadable signals, whether modulated using a carrier or not, include, butare not limited to, signals that a computer system hosting or running acomputer program can be configured to access, including signalsdownloaded through the Internet or other networks. Finally, the order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the process.

The example process 300 begins upon receiving an order for an item, asin 302. For example, a user may interact with an e-commerce system andplace an order for an item available for sale via the e-commerce system.The order for the item may identify the item, the delivery destination,and/or the materials handling facility from which the item is to bedelivered. For example, when a user places an order for an item, theuser may also specify a delivery destination to which the item is to bedelivered. Likewise, the inventory management system may determine amaterials handling facility that maintains an inventory of the item andspecify the materials handling facility as the location from which theitem is to be transported.

Upon receiving the order for the item, a UAV configuration necessary foraerial transport of the item from the materials handling facility to thedelivery destination is determined, as in 304. For example, the exampleprocess 300 may determine a size and/or weight of the ordered item, thedistance between the materials handling facility and the deliverydestination, current and/or anticipated weather conditions between thematerials handling facility and the delivery destination, etc. Based onthis information, the example process 300 may determine the requiredlifting capacity and estimated power necessary for a UAV to aeriallytransport the item from the materials handling facility to the deliverydestination.

Based on the determined UAV configuration for the ordered item, adetermination is made as to whether the item can be delivered using aone-way UAV, as in 306. For example, if the determined UAV configurationspecifies that the required carrying capacity of the UAV is greater thanthe carrying capacity of the one-way UAVs (e.g., one pound), it isdetermined that the item cannot be delivered using a one-way UAV.Likewise, if the UAV configuration specifies that the power required toaerially transport the item from the materials handling facility to thedelivery destination exceeds the available power of the one-way UAVs, itis determined that the item cannot be delivered using a one-way UAV.Other factors beyond carrying capacity and power may also be consideredin determining if the item can be delivered using a one-way UAV. Forexample, if the weather conditions (e.g., wind) between the materialshandling facility and the delivery destination exceed what can bewithstood by the one-way UAV, it may be determined that the one-way UAVcannot be utilized to deliver the item.

If it is determined that the item cannot be delivered using a one-wayUAV, the item is delivered using other forms of transport, as in 308.For example, the item may be delivered using a larger UAV that candeliver the item and return to the materials handling facility, oranother location, under its own power. Alternatively, the item may bedelivered using other delivery channels, such as ground-based delivery.

If it is determined that the item can be delivered using a one-way UAV,a one-way UAV that satisfies the determined UAV configuration isselected for use, as in 310. For example, as discussed above, multipleone-way UAV configurations (different sizes and/or power capabilities)may be available for delivery of items. Likewise, different one-way UAVconfigurations may include different sizes, shapes, and/or types ofpayload containers for use in carrying ordered items.

Upon selection of a one-way UAV, the ordered item (payload) and theone-way UAV are coupled together, as in 312. Coupling of the payload andthe one-way UAV may include, for example, placement of the payload intothe payload container of the one-way UAV, inserting the payload into amemory receiver, attaching the payload to the one-way UAV with straps,or other forms of coupling the payload to the one-way UAV. As will beappreciated, any form of coupling, joining, pairing, etc., of theone-way UAV with the payload such that the one-way UAV can aeriallytransport the payload may be considered herein as coupling the payloadto the one-way UAV.

Navigation instructions are also provided to the one-way UAV thatinstruct the UAV to aerially navigate from the materials handlingfacility to the delivery destination, as in 314. The navigationinstructions may include, for example, the coordinates of the deliverydestination, the desired altitude for aerial transport, the desiredspeed for transport, etc. In some implementations, the navigationinstructions may include a flight path that is to be followed by theone-way UAV as part of the delivery. In other implementations, theone-way UAV may generate and follow a flight path based on theinformation provided in the navigation instructions.

In some implementations, the one-way UAV may aerially transport thepayload from the materials handling facility to a delivery destinationusing the navigation instructions and without receiving any additionalinstructions. In other implementations, the one-way UAV may beconfigured to communicate with and/or receive information from otherUAVs, the materials handling facility, the delivery destination, and/orother sources that may be utilized in the navigation to the deliverydestination. For example, the one-way UAV may receive information fromother UAVs identifying obstacles, weather, or other information that theone-way UAV may utilize in navigating to the delivery destination. Insome implementations, navigation instructions may be provided to theone-way UAV while the one-way UAV is navigating to the deliverydestination. For example, the inventory management system 126 maytransmit navigation instructions to the one-way UAV while the one-wayUAV is navigating to the delivery destination. Transmission may beperformed using any type of wireless network, such as satellite,cellular, Wi-Fi, etc. In some implementations, the inventory managementsystem may transmit navigation instructions that include a UAVidentifier identifying the UAV that is to receive and use the navigationinstructions. Those navigation instructions may be sent to a first UAVand that first UAV may forward or transmit those instructions to asecond UAV. This process may continue until the intended UAV, such asthe one-way UAV receives the instructions.

In such an implementation, the computing capabilities of the one-way UAVmay be further reduced. Rather than receiving navigation instructionsand requiring the one-way UAV to determine and follow those navigationinstructions, the one-way UAV may receive individual navigationinstructions, such as increase/decrease altitude, alter speed and/ororientation, etc., and execute those commands. In some implementations,the one-way UAV may not include any navigation components. For example,the one-way UAV may include an imaging component (e.g., camera) thatcaptures images of an area (e.g., earth) near the one-way UAV andtransmits those images to the inventory management system. The inventorymanagement system may process the images to determine an approximatelocation, altitude, heading, speed, etc. of the one-way UAV. Forexample, the inventory management system may maintain images of theearth at known locations. Images received from the one-way UAV may becompared to the known images to determine the approximate location,altitude, heading, speed, etc. of the one-way UAV. Based on thedetermined approximate location, altitude, heading, speed, etc., theinventory management system may determine and send navigationinstructions to the one-way UAV.

Upon instructing the one-way UAV to navigate to the deliverydestination, the example process 300 completes, as in 316.

FIG. 4 is a flow diagram of a one-way UAV retrieval process 400,according to an implementation. The example process 400 begins bydetermining that a one-way UAV has completed delivery of its payload toa delivery destination, as in 402. For example, when the one-way UAVlands at a delivery destination, it may emit a signal or beaconconfirming that the one-way UAV has landed at the delivery destination.For example, the beacon may identify the one-way UAV and the location ofthe one-way UAV. In other examples, the beacon may not be transmitteduntil the payload container of the UAV is opened by the user and/or thepayload otherwise retrieved from the one-way UAV. In still anotherexample, the user may communicate with the inventory management systemto confirm that the item has been delivered. For example, as the one-wayUAV is navigating to the delivery destination, the inventory managementsystem may send a message to the user that the ordered item is in routeand will soon be delivered to the delivery destination. The message mayalso request that the user confirm when the item has been delivered.Upon receiving a user confirmation, it may be determined that the itemhas been delivered.

In still another example, the message to the user may request that theuser specify when they would like to have the one-way UAV retrieved.When the inventory management system receives a selection from the useras to when the one-way UAV is to be retrieved, it may be determined thatthe item has been delivered. In such an example, it may be assumed thatthe item has been delivered unless another notification is received fromthe user indicating that the item has not been delivered.

In still another example, item delivery may be assumed to occur at anestimated delivery time planned for the item delivery, unless anotification is subsequently received that the item was not delivered.

Upon determining that an item has or will be delivered, one or moreretrieval routes may be planned for a retrieval unit that includesretrieval of the one-way UAV, as in 404. A retrieval route may includemultiple retrieval locations from which one-way UAVs and/or other itemsare to be retrieved by the retrieval unit. For example, if multipleone-way UAVs are used to deliver items to different deliverydestinations within a defined distance of one another, the retrievalroute may be planned that routes a retrieval unit to each of thedelivery destinations, referred to as retrieval locations with respectto FIG. 4, for retrieval of the one-way UAVs. Likewise, if one or moreusers within the defined distance are returning, shipping, or otherwisehave indicated that an item is to be retrieved, the retrieval locationof those items may also be included in the retrieval route.

As the retrieval route is planned, it may be determined if a sufficientnumber of one-way UAVs and/or other items are scheduled for theretrieval route, as in 406. If it is determined that there are notsufficient one-way UAVs and/or other items planned for the retrievalroute, the example process 400 returns to block 402 and continues untila sufficient number of one-way UAVs and/or other items are planned forthe retrieval route. It may be determined that a sufficient number ofone-way UAVs and/or other items are planned for the retrieval route if,for example, the retrieval unit will be full once the one-way UAV and/orother items are retrieved or delivered, if all or a defined amount ofthe one-way UAVs in the defined distance within a defined period of timeare planned for retrieval, etc.

If it is determined that a sufficient number of one-way UAVs and/orother items are planned for retrieval along the retrieval route or asufficient number of other items are planned for delivery along theretrieval route, a determination is made as to whether the user(s) areto be notified of the planned retrieval(s), as in 408. For example, ifthe user is to place the one-way UAV at a specific retrieval location(e.g., on their porch, near the street, etc.) to facilitate retrievalwithout disrupting the user, it may be determined that the user is to benotified of the planned retrieval.

If it is determined that the user(s) are to be notified of the plannedretrieval, a message is sent to each user that is to be notifiedidentifying the approximate time of the planned retrieval and requestingthat the user place the one-way UAV at a location to facilitateretrieval of the one-way UAV, as in 410. For example, the user mayreceive an e-mail, SMS, MMS, and/or other message informing them of theplanned retrieval day and/or time and request that they place theone-way UAV at a location to facilitate retrieval.

Upon notifying the user(s) of the planned retrieval and/or if it isdetermined that user notification is not to be provided, the retrievalunit is instructed to navigate the retrieval route and retrieve theone-way UAV(s) and/or other item(s), as in 412. For example, if theretrieval unit is a ground-based vehicle, such as a truck, the retrievalroute may specify the streets that are to be navigated by thetransportation unit and the retrieval locations from which the one-wayUAVs and/or other items are to be retrieved. If the retrieval unit is anaerial retrieval unit, such as a larger UAV, the retrieval instructionsmay include navigation instructions, such as altitude, speed, and/orretrieval location coordinates that are utilized by the UAV to retrievethe one-way UAV(s) and/or other item(s).

FIG. 5 is a block diagram illustrating an example one-way UAV controlsystem 510 that may be utilized with any of the one-way UAVs discussedherein, such as the one-way UAV 212 of FIG. 2. In various examples, theblock diagram may be illustrative of one or more aspects of the one-wayUAV control system 510 that may be used to implement the various systemsand methods discussed herein and/or to control operation of the one-wayUAV. In the illustrated implementation, the one-way UAV control system510 includes a processor 502, motor controllers 504, such as electronicspeed controls (ESCs), a power supply module(s) 506 and/or a navigationsystem 508 coupled via an input/output (I/O) interface 511. The one-wayUAV control system 510 may also include other components such as acamera, a memory, e.g., a non-transitory computer readable storagemedium, etc. In some implementations, the memory may be removable fromthe one-way UAV. When the memory is inserted into a memory receiver ofthe one-way UAV, it may be utilized as the memory for the one-way UAVcontrol system 510 and include operating instructions that are executedby the processor 502. The memory may include navigation instructions foruse in causing the one-way UAV to navigate from a materials handlingfacility to a delivery destination.

In some implementations, the one-way UAV control system may also includea deactivation component configured to disable operability of theone-way UAV when the one-way UAV completes aerial navigation to thedelivery destination. For example, the deactivation component mayinclude a switch that disconnects the power module from the one-way UAVcontrol system and/or the motors, thereby disabling operability of theone-way UAV. In some implementations, the deactivation component maydeactivate the one-way UAV when the navigation instructions arecompleted, and/or when the one-way UAV lands at the deliverydestination.

The processor 502 may be any suitable processor capable of executinginstructions. For example, in various implementations, the processor 502may be a general-purpose or embedded processor implementing any of avariety of instruction set architectures (ISAs).

The memory may be configured to store executable instructions, data,navigation instructions, and/or other data accessible by the processor502. As discussed above, the memory may be part of the one-way UAVcontrol system 510 and/or removably coupled to the one-way UAV controlsystem 510. The memory may be implemented using any suitable memorytechnology, such as static random access memory (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory.

In one implementation, the I/O interface 511 may be configured tocoordinate I/O traffic between the processor(s) 502, the motorcontrollers 504, the navigation system 508, and/or other components ofthe one-way UAV. In some implementations, the I/O interface 511 mayperform any necessary protocol, timing or other data transformations toconvert data signals from one component (e.g., memory) into a formatsuitable for use by another component (e.g., processor 502). In someimplementations, the I/O interface 511 may include support for devicesattached through various types of peripheral buses, such as a variant ofthe Peripheral Component Interconnect (PCI) bus standard or theUniversal Serial Bus (USB) standard, for example.

The motor controllers 504 communicate with the navigation system 508 andadjust the rotational speed of each motor to stabilize the UAV and guidethe UAV to enable aerial navigation of the one-way UAV. The navigationsystem 508 may include a global positioning system (GPS), indoorpositioning system (IPS), or other similar system and/or sensors thatcan be used to navigate the UAV from a materials handling facility to adelivery destination.

In some implementations, the UAV may not include a navigation system 508or the navigation system may have decreased functionality. For example,rather than including GPS, IPS or other similar system, the navigationsystem 508 may only receive navigation instructions from the inventorymanagement system and send control commands to the motor controllers 504to execute the navigation instructions received from the inventorymanagement system. In such an example, the UAV may include a receiver(not shown) that is capable of receiving transmissions from theinventory management system. Likewise, the UAV may include a transmitterthat is capable of transmitting information to the inventory managementsystem. For example, the UAV may include an image capture device (e.g.,camera) that obtains images or video of the area surrounding the UAV andtransmits those images/video to the inventory management system. Theinventory management system may utilized the transmitted images todetermine the location of the UAV and generate navigation instructions.For example, the inventory management system may compare received imageswith images at known locations in the approximate area of the UAV todetermine the location, altitude, heading, speed, etc. of the UAV. Basedon the determined information, the inventory management system iscapable of generating and transmitting navigation instructions to theUAV that are executed by the UAV for navigation.

Those skilled in the art will appreciate that the UAV control system 510is merely illustrative and is not intended to limit the scope of thepresent disclosure. In particular, the control system may include anycombination of hardware or software that can perform the indicatedfunctions. The UAV control system 510 may also be connected to otherdevices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may, in some implementations, be combined infewer components or distributed in additional components. Similarly, insome implementations, the functionality of some of the illustratedcomponents may not be provided and/or other additional functionality maybe available.

FIG. 6 is a pictorial diagram of an illustrative implementation of aserver system 620 that may be used in the implementations describedherein. The server system 620 may include a processor 600, such as oneor more redundant processors, a video display adapter 602, a disk drive604, an input/output interface 606, a network interface 608, and amemory 612. The processor 600, the video display adapter 602, the diskdrive 604, the input/output interface 606, the network interface 608,and/or the memory 612 may be communicatively coupled to each other by acommunication bus 610.

The video display adapter 602 provides display signals to a display (notshown in FIG. 6) permitting an agent of the server system 620 to monitorand configure operation of the server system 620 and/or to provideinformation (e.g., regarding one-way UAV locations, utilization and/orretrieval plans). The input/output interface 606 likewise communicateswith external input/output devices not shown in FIG. 6, such as a mouse,keyboard, scanner, or other input and output devices that can beoperated by an agent of the server system 620. The network interface 608includes hardware, software, or any combination thereof, to communicatewith other computing devices. For example, the network interface 608 maybe configured to provide communications between the server system 620and other computing devices, such as that of a materials handlingfacility, delivery destination, retrieval container, etc., via anetwork.

The memory 612 generally comprises random access memory (RAM), read-onlymemory (ROM), flash memory, and/or other volatile or permanent memory.The memory 612 is shown storing an operating system 614 for controllingthe operation of the server system 620. A binary input/output system(BIOS) 616 for controlling the low-level operation of the server system620 is also stored in the memory 612.

The memory 612 additionally stores program code and data for providingnetwork services to the materials handling facility, inventorymanagement system 626, and/or retrieval route management system 628. Theprogram instructions enable communication with a data store managerapplication 621 to facilitate data exchange between the data stores 609,611, 613, 615, the inventory management system 626 and the retrievalroute management system 628.

As used herein, the term “data store” refers to any device orcombination of devices capable of storing, accessing, and retrievingdata, which may include any combination and number of data servers,databases, data storage devices and data storage media, in any standard,distributed or clustered environment. The server system 620 can includeany appropriate hardware and software for integrating with the datastores 609, 611, 613, and 615 as needed to execute aspects of one ormore applications for a materials handling facility, the inventorymanagement system 626, and/or the retrieval route management system 628.

The data stores 609, 611, 613, 615 can include several separate datatables, databases or other data storage mechanisms and media for storingdata relating to a particular aspect. For example, the inventory datastore 609 includes mechanisms for maintaining information related toitem inventory maintained by one or more materials handling facilities.Item inventory information may include, among other information, thequantity, size, shape, price, weight, and/or other information regardinginventory maintained in the materials handling facility.

The one-way UAV location data store 611 may maintain locationinformation for one-way UAVs that may be utilized by the inventorymanagement system 626 to plan item delivery of inventory items todelivery destinations and/or used by the retrieval route managementsystem for scheduling retrieval of one-way UAVs.

The UAV data store 613 may maintain information relating to one-way UAVconfigurations, carrying capacity, flight duration, power supply, etc.The information maintained in the UAV data store may be utilized by theinventory management system in determining if a one-way UAV may beutilized to transport an item from a materials handling facility to adelivery destination and/or to select a one-way UAV for item delivery.

The user profile data store 615 maintains information relating to users.For example, the user profile data store 615 may include deliverydestinations selected by users, user purchase history, user preferences(e.g. notification preferences), whether the user desires to haveone-way UAVs retrieved from a retrieval location, whether the user willprovide the one-way UAV to a retrieval container and/or whether the userprefers to send the one-way UAV back to a materials handling facility,or other location, using traditional transportation carriers, and thelike. The inventory management system 626 may utilize the user profileinformation to plan item delivery and/or communicate with the user. Theretrieval route management system may utilize the user profileinformation from the user profile data store to plan retrieval of theone-way UAVs.

It should be understood that there might be additional aspects that canbe stored in one or more of the data stores 609, 611, 613, 615 and thatadditional or fewer data stores beyond the ones illustrated may beincluded. The data stores 609, 611, 613, 615 are operable, through logicassociated therewith, to receive instructions from the server system 620and obtain, update or otherwise process data in response thereto.

The memory 612 may also include the inventory management system 626 andthe retrieval route management system 628, discussed above. Theinventory management system 626 and/or the retrieval route managementsystem 628 may be executable by the processor 600 to implement one ormore of the functions of the server system 620. In one implementation,the inventory management system 626 and/or the retrieval routemanagement system may represent instructions embodied in one or moresoftware programs stored in the memory 612. In another implementation,the inventory management system 626 can represent hardware, softwareinstructions, or a combination thereof.

The server system 620, in one implementation, is a distributedenvironment utilizing several computer systems and components that areinterconnected via communication links, using one or more computernetworks or direct connections. However, it will be appreciated by thoseof ordinary skill in the art that such a system could operate equallywell in a system having fewer or a greater number of components than areillustrated in FIG. 6. Thus, the depiction in FIG. 6 should be taken asbeing illustrative in nature and not limiting to the scope of thedisclosure.

Those skilled in the art will appreciate that in some implementationsthe functionality provided by the processes and systems discussed abovemay be provided in alternative ways, such as being split among moresoftware modules or processes or consolidated into fewer modules orprocesses. Similarly, in some implementations, illustrated processes andsystems may provide more or less functionality than is described, suchas when other illustrated processes instead lack or include suchfunctionality respectively, or when the amount of functionality that isprovided is altered. In addition, while various operations may beillustrated as being performed in a particular manner (e.g., in serialor in parallel) and/or in a particular order, those skilled in the artwill appreciate that, in other implementations, the operations may beperformed in other orders and in other manners.

The various processes and systems as illustrated in the figures anddescribed herein represent example implementations. The processes andsystems may be implemented in software, hardware, or a combinationthereof in other implementations. Similarly, the order of any method maybe changed and various elements may be added, reordered, combined,omitted, modified, etc., in other implementations.

From the foregoing, it will be appreciated that, although specificimplementations have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the appended claims and the elements recited therein. Inaddition, while certain aspects are presented below in certain claimforms, the inventors contemplate the various aspects in any availableclaim form. For example, while only some aspects may currently berecited as being embodied in a computer readable storage medium, otheraspects may likewise be so embodied. Various modifications and changesmay be made as would be obvious to a person skilled in the art havingthe benefit of this disclosure. It is intended to embrace all suchmodifications and changes and, accordingly, the above description is tobe regarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. An aerial vehicle, comprising: a payloadcontainer; a plurality of propellers, each propeller coupled to one of aplurality of motors; a power module coupled to the payload container andto the plurality of motors, wherein the power module is configured toprovide power to the plurality of motors to aerially transport an itemfrom a materials handling facility to a delivery destination; adeactivation component configured to disable operability of the aerialvehicle responsive to completion of aerial navigation to the deliverydestination; and wherein at least a portion of the aerial vehicle ismanufactured from a material that is recyclable or biodegradable.
 2. Theaerial vehicle of claim 1, wherein the item weighs less than one pound.3. The aerial vehicle of claim 1, further comprising: a memory receiverconfigured to receive a memory module that includes navigationinstructions; and wherein the item is the memory module and the memorymodule includes navigation instructions for aerially navigating theaerial vehicle from the materials handling facility to the deliverydestination.
 4. The aerial vehicle of claim 3, wherein the aerialvehicle is configured to follow the navigation instructions to aeriallynavigate from the materials handling facility to the deliverydestination, without receiving additional instructions.
 5. The aerialvehicle of claim 3, wherein the navigation instructions are configuredto be removed from memory module before the memory module is removedfrom the memory receiver of the aerial vehicle.
 6. The aerial vehicle ofclaim 1, wherein: the item is configured to be ordered, via anelectronic commerce system, by a user; the delivery destination isspecified by the user; the payload container is a cavity having foursides and a base; and the payload container is configured to at leastreceive the item.
 7. The aerial vehicle of claim 1, wherein the powermodule is configured to provide power that is sufficient to enableaerial transport of the item only from the materials handling facilityto the delivery destination and not back to the materials handlingfacility from the delivery destination.
 8. The aerial vehicle of claim1, wherein the aerial vehicle is a one-way aerial vehicle that is atleast one of recyclable, compostable, consumable, or disposable uponcompletion of an aerial transport of the item.
 9. An aerial vehicle,comprising: one or more propulsion mechanisms configured to propel theaerial vehicle; a power module coupled to at least one of the one ormore propulsion mechanisms, wherein the power module is configured toprovide power to transport an item from a materials handling facility toa delivery destination; a deactivation component configured to disablethe one or more propulsion mechanisms responsive to arrival of theaerial vehicle at the delivery destination; and a payload container thatis configured to at least receive the item.
 10. The aerial vehicle ofclaim 9, wherein: the item is configured to be ordered, via anelectronic commerce system, by a user; and the delivery destination isspecified by the user.
 11. The aerial vehicle of claim 9, furthercomprising: a memory receiver that is configured to receive a memorymodule, the memory module including navigation instructions for aeriallynavigating the aerial vehicle from the materials handling facility tothe delivery destination; and wherein the navigation instructions areconfigured to be deleted from the memory module before the memory modulemay be removed from the memory receiver of the aerial vehicle.
 12. Theaerial vehicle of claim 9, further comprising a control system that isconfigured to at least cause the deactivation component to disableoperability of the aerial vehicle responsive to completion of navigationby the aerial vehicle to the delivery destination.
 13. The aerialvehicle of claim 12, wherein the control system is further configured toat least determine that the aerial vehicle has completed aerialnavigation to the delivery destination by determining that the aerialvehicle has landed at the delivery destination.
 14. The aerial vehicleof claim 9, wherein the power module is configured to provide power thatis sufficient to enable aerial transport of the item only from thematerials handling facility to the delivery destination and not back tothe materials handling facility from the delivery destination.
 15. Theaerial vehicle of claim 9, wherein the deactivation component includes aswitch that is configured to selectively disconnect the power modulefrom the one or more propulsion mechanisms.
 16. The aerial vehicle ofclaim 9, further comprising: an image capture device that is configuredto capture an image of a space around the aerial vehicle; and acommunications system that is configured to at least send the image toan inventory management system.
 17. An aerial vehicle, comprising: aplurality of propulsion mechanisms configured to propel the aerialvehicle; a power module coupled to the plurality of propulsionmechanisms, wherein the power module is configured to provide power totransport an item from a materials handling facility to a deliverydestination; a payload container that includes a lid; a plurality ofradial arms extending away from the payload container; wherein: thepayload container is configured to at least receive the item; the lidincludes at least a portion of a control system; and each of thepropulsion mechanisms is coupled to a respective one of the radial arms;and a deactivation component configured to disable the plurality ofpropulsion mechanisms responsive to arrival of the aerial vehicle at thedelivery destination.
 18. The aerial vehicle of claim 17, wherein: theitem is configured to be ordered, via an electronic commerce system, bya user; and the delivery destination is specified by the user.
 19. Theaerial vehicle of claim 17, wherein the control system is configured toat least cause a signal to be transmitted from the aerial vehicleresponsive to opening of the lid of the payload container to confirm adelivery of the item.
 20. The aerial vehicle of claim 17, wherein thecontrol system is configured to at least cause the deactivationcomponent to disable one or more of the plurality of propulsionmechanisms responsive to completion of a navigation by the aerialvehicle to the delivery destination.